x448: use full coordinates #1
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All of the original authors have agreed to make this change
|
Uh, I'm not sure whats going on here. Do you want me to merge X448 into the RustCrypto#1306 PR? |
…ontgomeryXpoint`
|
I guess that was too early. That was to split the fixes that will need to go in x448 for when it merges. |
baloo
force-pushed
the
baloo/x448-full-coordinates
branch
from
c176c7e to
f799e52
Compare
daxpedda
force-pushed
the
curve448-4
branch
2 times, most recently
from
dce0a03 to
ce00799
Compare
daxpedda
force-pushed
the
curve448-4
branch
3 times, most recently
from
44f8c53 to
874805c
Compare
daxpedda
force-pushed
the
curve448-4
branch
15 times, most recently
from
fd154c5 to
3731d21
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a followup to RustCrypto#1250 to play nice with RustCrypto#1306